Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(forwarder): set content-encoding on override #305

Merged
merged 1 commit into from
Jun 14, 2024
Merged

Conversation

jta
Copy link
Contributor

@jta jta commented Jun 14, 2024

We currently rely on the S3 object being written with the correct content-encoding. There are many cases, such as vpcflowlogs, where the content-type is set to gz and the content-encoding is left blank.

This commit ensures we always set the content-encoding correctly for filenames that end in .gz

@jta jta force-pushed the joao/gzip-override branch 2 times, most recently from d1af7bc to 318182c Compare June 14, 2024 17:21
@jta jta marked this pull request as ready for review June 14, 2024 17:42
We currently rely on the S3 object being written with the correct
content-encoding. There are many cases, such as `vpcflowlogs`, where the
content-type is set to `gz` and the content-encoding is left blank.

This commit ensures we always set the content-encoding correctly for
filenames that end in `.gz`
@jta jta merged commit 23bf023 into main Jun 14, 2024
16 checks passed
@jta jta deleted the joao/gzip-override branch June 14, 2024 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants